Feature: metadata_scan supports checking the metadata of index table now #21800
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
XuPeng-SH
requested changes
May 8, 2025
heni02
approved these changes
May 19, 2025
XuPeng-SH
approved these changes
May 19, 2025
7 tasks
XuPeng-SH
added a commit
that referenced
this pull request
May 21, 2025
…able (#21872) ## What type of PR is this? - [ ] API-change - [ ] BUG - [ ] Improvement - [ ] Documentation - [x] Feature - [ ] Test and CI - [ ] Code Refactoring ## Which issue(s) this PR fixes: issue #21785 ## What this PR does / why we need it: Same as PR #21800 --------- Co-authored-by: XuPeng-SH <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
Which issue(s) this PR fixes:
issue #21785
What this PR does / why we need it:
MO without this PR
metadata_scan currently only supports scanning regular tables.
For example, let's say there is a database named cabbage ,a table named user, and an index named idx_username which corresponds to the table __mo_index_unique_0196a9ae-33d9-7308-9d57-8a593fc55dbf.
We can check the metadata of user as follows.
But we can't check the metadata of index tables even if we know the system-generated name of the index table.
MO with this PR
Now we can easily check the metadata of an index table by grammar metadata_scan("db_name.table_name.?index_name", "col_name")g;
After review
The current grammar is metadata_scan("db_name.table_name.?index_name", "col_name")g;